![]() | ![]() | ![]() | ![]() |
In SAS Information Map Studio 4.4 and later, you might see an error when attempting to create or open an OLAP-based information map that contains a filter. The exact behavior depends on the following conditions:
The first two issues should be resolved in 4.4_M1 and later. However, the third condition is not resolved in any release.
For new information maps, if you add the filter before you save the information map the first time, then you might not be able to re-open the information map. You see the following error.
The application is unable to open the information map "xxxx" because it was saved with more recent software.
You can continue to use the information map in applications such as SAS® Web Report Studio. However, you cannot modify the information map. To resolve this issue, upgrade to the latest release of SAS Information Map Studio.
For existing information maps that do not contain any filters, then you might see the following error when you attempt to save the information map after you add a filter.
com.sas.iquery.metadata.MetadataException: Saving the information map "xxxx" failed because saving would require an upgrade of the information map's minor version number and the save option permitting the upgrade was not specified. Minor version increases can cause older software to no longer be able to use certain features of the information map such as updating, copying and deleting it.
Your only option at this point is to click OK in the message and delete the filter that you created. You cannot add a filter to the information map. However, you can continue to use the information map without the filter in applications such as SAS Web Report Studio.
To resolve this issue, upgrade to the latest release of SAS Information Map Studio.
You might see the error shown previously if your information map was originally created in a locale that is different than the one you are now using to edit the information map. This problem can occur even if you are using release 4.4_M1 or later. Here are two examples:
If you are using release 4.4_M1 or later, you can work around this issue by editing the information map in the same locale in which it was created.
Some customers who are not using different locales have reported this problem at release 4.4_M1 or later. If you running release 4.4_M1 or later and you are not mixing locales, then the only solution is to recreate the information map.
Product Family | Product | System | Product Release | SAS Release | ||
Reported | Fixed* | Reported | Fixed* | |||
SAS System | SAS Information Map Studio | Microsoft® Windows® for x64 | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 |
Microsoft Windows 8 Enterprise 32-bit | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows 8 Enterprise x64 | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows 8 Pro 32-bit | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows 8 Pro x64 | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows 8.1 Enterprise 32-bit | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows 8.1 Enterprise x64 | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows 8.1 Pro | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows 8.1 Pro 32-bit | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows Server 2008 R2 | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows Server 2008 for x64 | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows Server 2012 Datacenter | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows Server 2012 R2 Datacenter | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows Server 2012 R2 Std | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Microsoft Windows Server 2012 Std | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Windows 7 Enterprise x64 | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 | ||
Windows 7 Professional x64 | 4.4 | 4.4_M1 | 9.4 TS1M0 | 9.4 TS1M1 |